Sourced from alembic's releases.

1.19.1

Released: August 8, 2026

bug

• [bug] [autogenerate] Fixed bug in the check constraint detection implemented in #508 that failed to take into account column bound check constraints, leading to wrong autogenerate detections.

  References: #1842

• See full diff in compare view

Sourced from charset-normalizer's releases.

Version 3.5.0

3.5.0 (2026-08-12)

Added

• Explicit support for Python 3.15

Fixed

• Comparing a CharsetMatch to a non-alias encoding strings (#773)
• Return 0.0 CharsetMatch.multi_byte_usage for empty payloads instead of crashing (#774)
• A file with both a charset declaration and BOM/SIG did not verify first the BOM/SIG charset.
• iso2022* cases misdetected due to a flaw in our multibyte chunking logic.

Changed

• Replaced the optional mypyc build with Cython extensions while retaining the pure Python fallback. The previous engine (mypyc) started to hit rough limit around the optimization of our noise/coherence detector while Cython allows us to steer the engine toward the right generated optimized sources. This change SHOULD not impact bundler (e.g. Pyinstaller) as the module are immediately discoverable (i.e. not hidden import like mypyc did). Moreover, a long wished distribution is the abi3 wheels, this will allow us to no longer rush each year when a new Python interpreter is released. We still distribute the interpreter specific wheels for faster performance.
• Applied micro-optimization on several utils.
• CharsetMatches no longer sort on each match insertion.

Misc

• Removed an old performance optimization attempt in apy.py (success_fast_tracked+payload_result_cache).

Sourced from charset-normalizer's changelog.

3.5.0 (2026-08-12)

Added

• Explicit support for Python 3.15

Fixed

• Comparing a CharsetMatch to a non-alias encoding strings (#773)
• Return 0.0 CharsetMatch.multi_byte_usage for empty payloads instead of crashing (#774)
• A file with both a charset declaration and BOM/SIG did not verify first the BOM/SIG charset.
• iso2022* cases misdetected due to a flaw in our multibyte chunking logic.

Changed

• Replaced the optional mypyc build with Cython extensions while retaining the pure Python fallback. The previous engine (mypyc) started to hit rough limit around the optimization of our noise/coherence detector while Cython allows us to steer the engine toward the right generated optimized sources. This change SHOULD not impact bundler (e.g. Pyinstaller) as the module are immediately discoverable (i.e. not hidden import like mypyc did). Moreover, a long wished distribution is the abi3 wheels, this will allow us to no longer rush each year when a new Python interpreter is released. We still distribute the interpreter specific wheels for faster performance.
• Applied micro-optimization on several utils.
• CharsetMatches no longer sort on each match insertion.

Misc

• Removed an old performance optimization attempt in apy.py (success_fast_tracked+payload_result_cache).

• 3325d87 Merge pull request #792 from jawah/update-cibuildwheel-action
• 77203b1 chore: reformat noxfile.py
• 8561c22 chore(deps): bump github/codeql-action/upload-sarif (#787)
• 25248df chore(deps): bump actions/setup-python from 6.3.0 to 7.0.0 (#789)
• 3eaaf3e chore: enable cp315t in ci
• fbe9fc4 chore: update cibuildwheel for py315 by default
• 5c7b82a chore: add emscripten classifier
• 7d30c21 chore: skip pyodide tests cibw
• 417d66f Merge pull request #791 from jawah/patch-1
• 130afd5 chore: perf script initial warm with big5 dummy content
• Additional commits viewable in compare view

Sourced from greenlet's changelog.

3.5.5 (2026-08-10)

• Link the C++ runtime statically into the Windows wheels again, as the Appveyor builds did through 3.3.0. Since 3.3.1 _greenlet.pyd imported MSVCP140.dll, which no Windows CPython distribution ships, so importing greenlet failed on machines without the Visual C++ redistributable. See issue 525 <https://github.com/python-greenlet/greenlet/issues/525>_. Issue and pull request by Daniel Sticker.

.. note:: Binary 3.15 wheels are now built with 3.15.0rc1. This should be compatible with future 3.15 releases and is believed compatible with 3.15b4 as well (but not earlier versions).

• ddb1453 Preparing release 3.5.5
• 7de515c Update CHANGES: Credit for issue 525 and note about 3.15 binary wheels [skip ci]
• f3746aa Merge pull request #526 from stickerdaniel/windows-static-runtime
• f1ce3ca Restore static linking of the C++ runtime for Windows wheels
• b6690a5 Merge pull request #523 from python-greenlet/dependabot/github_actions/github...
• 726cc38 Bump the github-actions group with 3 updates
• e5c5f4c Merge pull request #522 from ddorian/c-stack-refs-test-detection
• be55a59 Check that the suspended greenlet is what keeps the class alive
• e9c01dd Back to development: 3.5.5
• See full diff in compare view

Sourced from numpy's releases.

v2.5.2 (Aug 9, 2026)

NumPy 2.5.2 Release Notes

The NumPy 2.5.2 is a patch release that fixes bugs discovered after the 2.5.1 release. The big news is that it includes wheels for the newly released Python 3.15.0rc1.

This release supports Python versions 3.12-3.15

C API changes

PyArray_StringDTypeObject is opaque under the abi3t stable ABI

The PyArray_StringDTypeObject was accidentally exposed in NumPy 2.5 when targeting the free-threading-compatible stable ABI (Py_TARGET_ABI3T). PyArray_StringDTypeObject is now an opaque struct: extensions compiled that way cannot access its fields, since the struct layout depends on the size of the object header. Any code that accessed PyArray_StringDTypeObject fields in an abi3t build would have crashed, so we are making this API change in a bugfix release.

The NpyString allocator API remains usable by passing the descriptor object pointer, e.g. NpyString_acquire_allocator((PyArray_StringDTypeObject *)descr).

(gh-31771)

Contributors

A total of 16 people contributed to this release. People with a "+" by their names contributed a patch for the first time.

• Abhijeetsingh Meena +
• Charalampos Stratakis
• Charles Harris
• Chris Ninham +
• David Woods
• Geonho +
• Gopu Yeshwanth Reddy +
• Iason Krommydas
• Ijtihed Kilani
• Jelle Zijlstra +
• Joren Hammudoglu
• Kumar Aditya
• Mike Boyle
• Nathan Goldbaum
• Raghuveer Devulapalli
• Sebastian Berg

... (truncated)

• 48fecee REL: Prepare for the NumPy 2.5.2 release (#32226)
• ecf599c Merge pull request #32221 from charris/backport-32151
• 3c7ac97 Merge pull request #32220 from charris/backport-32205
• 23b30f4 BUG: avoid segfaults when legacy copyswap slot is not defined (#32151)
• 4964ca8 TYP: isclose shape-typing fix for 2d array-likes (#32205)
• c37ed94 MAINT: Skip limited_api tests on some platforms. (#32214)
• 5cfd73b Merge pull request #32206 from charris/update-cibuildwheel
• d8262bc MAINT: Update cibuildwheel to v4.2.0
• 988d94d Merge pull request #32158 from charris/backport-32133
• b2e4f97 BUG: avoid possible stack overflow in arraydescr_dealloc (#32133)
• Additional commits viewable in compare view

• e605afe Prep for 9.0.37 release
• 9bf1822 Generated files for metadata
• f3e59e7 Merge metadata changes from upstream 9.0.37
• See full diff in compare view

• See full diff in compare view

Sourced from sentry-sdk[fastapi]'s releases.

2.68.0

Important

• We're making enable_logs and enable_metrics no-op with this release (#7177), and they'll be dropped in the next major.

  Previously, enable_logs also controlled automatic logs collection from the logging and Loguru integrations. These integrations now get an integration-level capture_sentry_logs boolean option to allow for more control over the auto-collection. These options are False by default, i.e., nothing is auto-collected without your explicit opt-in.

  Action Needed

  If you had enable_logs set to True:

  • If you were using the sentry_sdk.logger.X API, no action necessary, the API will just work.
  • If you were auto-collecting logs from either LoggingIntegration or LoguruIntegration, the auto-collection will be turned off in this release. You can switch auto-collection on explicitly with:

  import sentry_sdk
  from sentry_sdk.integrations.logging import LoggingIntegration
  from sentry_sdk.integrations.loguru import LoguruIntegration
  sentry_sdk.init(
  integrations=[
  LoggingIntegration(capture_sentry_logs=True),
  LoguruIntegration(capture_sentry_logs=True),
  ],
  )

  If you had enable_logs set to False:

  • If you were using it to gate usages of the sentry_sdk.logger.X API, you'll need to remove the calls entirely or define a before_send_log callback to filter out unwanted logs.

  If you has enable_metrics set to False:

  • Any metrics emitted using the metrics API will be emitted. You'll need to drop them in a before_send_metric or remove the calls to the API.

  Why We're Doing This

  We recognize this is a disruptive change for some folks and want to make it clear this is a one-off. We're removing the options because they were an unnecessary hurdle that one had to jump through to be able to use logs and metrics, and it was confusing why the logging API would not just work on its own. On the other hand, we wanted to give you more fine-grained control over automatic collection.

New Features ✨

Other

• Set the segment source on the scope for NoOpStreamedSpan by @​alexander-alderman-webb in #7163
• Remove early return for NoOpStreamedSpan in set_transaction_name() by @​alexander-alderman-webb in #7164
• Set the segment name on the scope with NoOpStreamedSpan by @​alexander-alderman-webb in #7162

Bug Fixes 🐛

• (batcher) Add global flush trigger based on the span number by @​alexander-alderman-webb in #7150

Internal Changes 🔧

... (truncated)

Sourced from sentry-sdk[fastapi]'s changelog.

2.68.0

Important

• We're making enable_logs and enable_metrics no-op with this release (#7177), and they'll be dropped in the next major.

  Previously, enable_logs also controlled automatic logs collection from the logging and Loguru integrations. These integrations now get an integration-level capture_sentry_logs boolean option to allow for more control over the auto-collection. These options are False by default, i.e., nothing is auto-collected without your explicit opt-in.

  Action Needed

  If you had enable_logs set to True:

  • If you were using the sentry_sdk.logger.X API, no action necessary, the API will just work.
  • If you were auto-collecting logs from either LoggingIntegration or LoguruIntegration, the auto-collection will be turned off in this release. You can switch auto-collection on explicitly with:

  import sentry_sdk
  from sentry_sdk.integrations.logging import LoggingIntegration
  from sentry_sdk.integrations.loguru import LoguruIntegration
  sentry_sdk.init(
  integrations=[
  LoggingIntegration(capture_sentry_logs=True),
  LoguruIntegration(capture_sentry_logs=True),
  ],
  )

  If you had enable_logs set to False:

  • If you were using it to gate usages of the sentry_sdk.logger.X API, you'll need to remove the calls entirely or define a before_send_log callback to filter out unwanted logs.

  If you has enable_metrics set to False:

  • Any metrics emitted using the metrics API will be emitted. You'll need to drop them in a before_send_metric or remove the calls to the API.

  Why We're Doing This

  We recognize this is a disruptive change for some folks and want to make it clear this is a one-off. We're removing the options because they were an unnecessary hurdle that one had to jump through to be able to use logs and metrics, and it was confusing why the logging API would not just work on its own. On the other hand, we wanted to give you more fine-grained control over automatic collection.

New Features ✨

Other

• Set the segment source on the scope for NoOpStreamedSpan by @​alexander-alderman-webb in #7163
• Remove early return for NoOpStreamedSpan in set_transaction_name() by @​alexander-alderman-webb in #7164
• Set the segment name on the scope with NoOpStreamedSpan by @​alexander-alderman-webb in #7162

Bug Fixes 🐛

• (batcher) Add global flush trigger based on the span number by @​alexander-alderman-webb in #7150

... (truncated)

• c819e66 Update README
• 90446df Update CHANGELOG.md
• cb2499c release: 2.68.0
• 1c3b50d ref: Flush trace buckets when segment spans finish (#7170)
• c200bdf test(django): Remove dead code and stale markers from the Django test suite (...
• 4e4ea83 ref(boto3): Move crumbs to integration (#7165)
• 0f0cd1f ref(stdlib): Move crumbs to integration (#7161)
• 2fef9bc chore: Make enable_logs, enable_metrics no-op (#7177)
• 8177739 ref(httpx,httpx2): Move crumbs to integrations (#7149)
• e4d7398 ref(pyreqwest): Move crumbs to integration (#7148)
• Additional commits viewable in compare view

Sourced from sqlalchemy's releases.

2.0.52

Released: August 11, 2026

platform

• [platform] [bug] Python 3.15 support has been added and tested, including minimal changes for full compatibility.

  References: #13477

orm

• [orm] [bug] Fixed a result-column misalignment bug in ORM-enabled UPDATE statements where synchronize_session="fetch" is in use, either explicitly or because the statement uses constructs such as CTEs that implicitly select for it. Columns in rows returned by .returning() could be returned under incorrect keys (e.g. row[SomeClass.a] returning the value of a different column), a problem most likely to manifest under concurrent workloads. ORM DELETE statements were not affected.

  References: #13439

• [orm] [bug] Fixed bug where a failed _orm.Session.bulk_insert_mappings(), _orm.Session.bulk_update_mappings() or _orm.Session.bulk_save_objects() call could leave the _orm.Session permanently in a "flushing" state, such as when the transaction could not be begun because a previous flush had left it needing a rollback. Unlike _orm.Session.flush(), the bulk methods set the internal flushing flag and began the transaction outside of the try/finally block that resets it, so that neither _orm.Session.rollback() nor _orm.Session.close() would clear it, and every subsequent flush would raise InvalidRequestError: Session is already flushing. Pull request courtesy Hamody We.

  References: #13485

• [orm] [bug] Fixed issue where unpickling an ORM object that were loaded using loader options making use of wildcard tokens, such as _orm.load_only() or _orm.raiseload() with "*", would fail with KeyError or IndexError if the process doing the unpickling had not yet constructed a loader path making use of that same token. This would typically be observed when the object were unpickled in a separate process, such as with the spawn or forkserver multiprocessing start methods, the latter of which became the default on POSIX platforms as of Python 3.14. The internal collection of these tokens is now established up front, so that it is identical in every process.

... (truncated)

• See full diff in compare view

Sourced from starlette's releases.

Version 1.6.0

What's Changed

• Add max_body_size to Starlette and route classes by @​Kludex in Kludex/starlette#3431
• Expose http.response.debug info via response extensions by @​y2kbugger in Kludex/starlette#3130

New Contributors

• @​y2kbugger made their first contribution in Kludex/starlette#3130

Full Changelog: Kludex/starlette@1.5.1...1.6.0

Version 1.5.1

What's Changed

• Reject inverted single-byte Range like bytes=5-4 by @​nikolauspschuetz in encode/starlette#3389
• Limit FileResponse to 100 ranges by @​Kludex in encode/starlette#3430

Full Changelog: Kludex/starlette@1.5.0...1.5.1

Version 1.5.0

This release is all about giving GZipMiddleware some love. 🗜️

What's Changed

• Add exclude_content_types parameter to GZipMiddleware by @​Kludex in encode/starlette#3418
• Flush GZip output for each streamed chunk by @​Kludex in encode/starlette#3419
• Skip compression of partial responses in GZipMiddleware by @​Kludex in encode/starlette#3420
• Expand default excluded content types in GZipMiddleware by @​Kludex in encode/starlette#3421

Full Changelog: Kludex/starlette@1.4.1...1.5.0

Sourced from starlette's changelog.

1.6.0 (August 8, 2026)

Added

• Add max_body_size to Starlette and route classes #3431.
• Expose http.response.debug information via response extensions #3130.

1.5.1 (August 8, 2026)

Fixed

• Reject inverted single-byte ranges in FileResponse #3389.
• Limit FileResponse to 100 ranges #3430.

1.5.0 (August 8, 2026)

Added

• Add exclude_content_types parameter to GZipMiddleware #3418.

Changed

• Expand default excluded content types in GZipMiddleware #3421.

Fixed

• Flush GZip output for each streamed chunk #3419.
• Skip compression of partial responses in GZipMiddleware #3420.

• 4f250d6 Version 1.6.0 (#3434)
• 9eea41a Expose http.response.debug info via response extensions (#3130)
• 38f8999 Add max_body_size to Starlette and route classes (#3431)
• c41236c Version 1.5.1 (#3432)
• 9c500db Limit FileResponse to 100 ranges (#3430)
• 78ae82c Reject inverted single-byte Range like bytes=5-4 (#3389)
• c1d6eda chore(deps): bump pymdown-extensions from 11.0 to 11.0.1 (#3429)
• ee66ca4 chore(deps): bump the python-packages group across 1 directory with 8 updates...
• 00d1016 fix(tests): skip test_staticfiles_filename_too_long on Windows where os.pathc...
• d96887e Add Pydantic Logfire banner to the docs (#3428)
• Additional commits viewable in compare view

Sourced from typing-inspection's releases.

v0.4.3 2026-08-10

What's Changed

• Drop support for Python 3.9 by @​Viicos in #52
• Avoid module getattr() calls in typing_objects functions by @​Viicos in #57
• Add Python 3.15 support by @​Viicos in #59

Full Changelog: pydantic/typing-inspection@v0.4.2...v0.4.3

Sourced from typing-inspection's changelog.

v0.4.4 (2026-08-12)

• Add typing_objects.DEPRECATED_ALIASES_ID by @​Viicos in #63

v0.4.3 (2026-08-10)

• Drop support for Python 3.9 by @​Viicos in #52
• Avoid module getattr() calls in typing_objects functions by @​Viicos in #57
• Add Python 3.15 support by @​Viicos in #59

• 83d4dbb Prepare release v0.4.4 (#64)
• 3ac9791 Fixes to DEPRECATED_ALIASES_IDS (#65)
• 382616c Add typing_objects.DEPRECATED_ALIASES_IDS (#63)
• cef71ba Fix docs publish CI job (#62)
• 7b09e7a Fix coverage CI job (#61)
• 2648bdf Prepare release 0.4.3 (#60)
• 7c14c75 Add Python 3.15 support (#59)
• 677b2ae Fix docs publish CI permissions (#58)
• 5e33e8d Avoid module getattr() calls in typing_objects functions (#57)
• f576d83 Fix Literal test (#56)
• Additional commits viewable in compare view

Sourced from uvicorn's releases.

Version 0.52.3

Changed

• Update zttp to 0.0.24 and use its combined receive path, improving HTTP/1.1 request parsing performance (#3067)

Full Changelog: Kludex/uvicorn@0.52.2...0.52.3

Version 0.52.2

Fixed

• Update zttp to 0.0.22, fixing bodyless request receives and improving HTTP/1 request parsing performance (#3063)

Full Changelog: Kludex/uvicorn@0.52.1...0.52.2

Sourced from uvicorn's changelog.

0.52.3 (August 13, 2026)

Changed

• Update zttp to 0.0.24 and use its combined receive path, improving HTTP/1.1 request parsing performance (#3067)

0.52.2 (August 13, 2026)

Fixed

• Update zttp to 0.0.22, fixing bodyless request receives and improving HTTP/1 request parsing performance (#3063)

• a68da60 Version 0.52.3 (#3068)
• 6e3bb4c Use zttp 0.0.24 fast receive path (#3067)
• 2a5ff18 Version 0.52.2 (#3066)
• 1920297 Update zttp to 0.0.22 (#3063)
• 5c560da chore(deps): bump pymdown-extensions from 11.0 to 11.0.1 (#3061)
• See full diff in compare view

Sourced from pre-commit's releases.

pre-commit v4.6.2

Fixes

• Fix language: node hooks that contain "scripts": {"build": ...} with npm 11.x.
  • Regressed in 4.6.1.
  • #3737 issue by @​mheiges.
  • #3743 PR by @​asottile.

Sourced from pre-commit's changelog.

4.6.2 - 2026-08-10

Fixes

• Fix language: node hooks that contain "scripts": {"build": ...} with npm 11.x.
  • Regressed in 4.6.1.
  • #3737 issue by @​mheiges.
  • #3743 PR by @​asottile.

• 9767b6c v4.6.2
• 42ee3ff Merge pull request #3743 from pre-commit/npm-build-scripts-11-x
• 3056619 fix language: node for hooks with build scripts and npm 11.x
• See full diff in compare view

Sourced from filelock's releases.

3.32.3

What's Changed

• 🧪 test(strict): deflake close-fault injections on graalpy by @​gaborbernat in tox-dev/filelock#697
• 📄 docs: publish llms.txt from the docs build by @​gaborbernat in tox-dev/filelock#700
• 🐛 fix(fork): survive audit events during interpreter shutdown by @​gaborbernat in tox-dev/filelock#703

Full Changelog: tox-dev/filelock@3.32.2...3.32.3

Sourced from filelock's changelog.

########### Changelog ###########

.. towncrier-draft-entries:: Unreleased

.. towncrier release notes start

---

3.32.3 (2026-08-13)

---

• The fork-safety audit hook no longer prints Exception ignored in audit hook with a TypeError when an audit event fires during interpreter shutdown, after CPython has already cleared the module globals. :pr:701

---

3.32.2 (2026-07-29)

---

• A SoftReadWriteLock or SoftFileLease acquire whose heartbeat thread fails to start now unlinks its marker and hands the claim back, instead of leaving an unrefreshed marker a peer takes while the caller believes it still holds the lock. :pr:691

---

3.32.1 (2026-07-26)

---

• Canceling an AsyncSoftReadWriteLock acquire now releases the claim instead of leaking a marker whose heartbeat wedges every contender. :pr:686

---

3.32.0 (2026-07-21)

---

• SoftReadWriteLock closes the directory handle it opens to scan for readers as soon as a scan stops early, rather than holding it until the generator is collected. :pr:685
• Declare support for Python 3.15 and run the test suite against it and its free-threaded build, both currently in beta. :pr:683
• The source distribution ships the capability probes the tests import, and reading one no longer needs coverage installed, so the suite runs from an unpacked sdist instead of failing on a missing coverage_pragmas. :pr:685

---

3.31.2 (2026-07-21)

---

• filelock imports again on runtimes whose errno omits ENOTSUP, such as GraalPy, where importing the package raised ImportError. It probes the code instead, preferring ENOTSUP, falling back to EOPNOTSUPP where that name is absent, and dropping to ENOSYS/EXDEV where neither exists. Platforms defining ENOTSUP keep their behavior. :pr:681

---

... (truncated)

• 4aa742c Release 3.32.3
• fb5ab3e 🐛 fix(fork): survive audit events during interpreter shutdown (#703)
• 35f759c 📄 docs: publish llms.txt from the docs build (#700)
• 4b6e966 [pre-commit.ci] pre-commit autoupdate (#699)
• 0e0f666 build(deps): bump pypa/gh-action-pypi-publish from 1.14.1 to 1.14.2 (#698)
• 6689d82 🧪 test(strict): deflake close-fault injections on graalpy (#697)
• df67bf7 [pre-commit.ci] pre-commit autoupdate (#696)
• See full diff in compare view

Sourced from rasterio's releases.

1.5.1

Version 1.5.1 fixes a number of bugs and unblocks the release of affine 3.0.0.

Thanks for being patient, folks! It's a weird time in the open source software world.

Bug fixes

• DatasetBase.__dealloc__ has been removed and replaced by a __del__ method modeled after that of io.IOBase. This eliminates cryptic partial error messages from being printed as rio-calc finishes and finalizes (gh-3612).
• The "bbox" attribute of GeoJSON data is no longer used by features.bounds() when optional parameters (transform and/or north_up=False) are provided. An unreported bug where transformation matrices were not applied to feature and geometry collections has also been fixed (gh-3609).
• The size guard in sieve() was defective for 3D sources and has been fixed (gh-3606). As a side benefit, the dimensionality of output has been made consistent with the read() method of datasets: 3D output is no longer automatically squeezed to 2D. The previous behavior was a bug.
• A test of subdataset support is skipped for GDAL versions >= 3.13.0 (gh-3534). The most recent versions of GDAL have a netCDF filename parsing defect.
• Acknowledge new runtime warnings about invalid type casting using numpy (gh-3599).
• Acknowledge the Python deprecation warnings from using "fork" start mode in testing warp error propagation (gh-3600).
• Eliminate numpy deprecation warnings by reshaping views instead of setting their shape attributes (gh-3592).
• Require pyparsing version >= 3.0 to eliminate a deprecation warning for use of parseString (gh-3551).
• Remove a dependency on unmainted cligj by bringing some CLI options back into Rasterio (gh-3550).
• Avoid a ValueError in reproject() when using a "==" comparison between array masks and np.ma.nomasked (gh-3531).

Documentation

• Note that PROJ transformation grids and the PROJ_NETWORK environment variable are required to apply vertical (datum) shifts when reprojecting or transforming (gh-2929).

Dependencies

• Rasterio 1.5.1 is compatible with affine versions 3.0rc1 and newer.

Packaging:

• Wheels include GDAL 3.12.4, netCDF 4.10.1, cURL 8.20.0, and PROJ 9.8.1. Python 3.15 is supported for the first time.

Sourced from rasterio's changelog.

1.5.1 (2026-08-07)

Bug fixes:

• DatasetBase.dealloc has been removed and replaced by a del method modeled after that of io.IOBase. This eliminates cryptic partial error messages from being printed as rio-calc finishes and finalizes (gh-3612).
• The "bbox" attribute of GeoJSON data is no longer used by features.bounds() when optional parameters (transform and/or north_up=False) are provided. An unreported bug where transformation matrices were not applied to feature and geometry collections has also been fixed (gh-3609).
• The size guard in sieve() was defective for 3D sources and has been fixed (gh-3606). As a side benefit, the dimensionality of output has been made consistent with the read() method of datasets: 3D output is no longer automatically squeezed to 2D. The previous behavior was a bug.
• A test of subdataset support is skipped for GDAL versions >= 3.13.0 (gh-3534). The most recent versions of GDAL have a NetCDF filename parsing defect.
• Acknowledge new runtime warnings about invalid type casting using numpy (gh-3599).
• Acknowledge the Python deprecation warnings from using "fork" start mode in testing warp error propagation (gh-3600).
• Eliminate numpy deprecation warnings by reshaping views instead of setting their shape attributes (gh-3592).
• Require pyparsing version >= 3.0 to eliminate a deprecation warning for use of parseString (gh-3551).
• Remove a dependency on unmaintained cligj by bringing some CLI options back into Rasterio (gh-3550).
• Avoid a ValueError in reproject() when using a "==" comparison between array masks and np.ma.nomasked (gh-3531).

Documentation:

• Note that PROJ transformation grids and the PROJ_NETWORK environment variable are required to apply vertical (datum) shifts when reprojecting or transforming (gh-2929).

Dependencies:

• Rasterio 1.5.1 is compatible with affine versions 3.0rc1 and newer.

Packaging:

• Wheels include GDAL 3.12.4, netCDF 4.10.1, cURL 8.20.0, and PROJ 9.8.1.

• 2feebab Rel 1.5.1 (#3614)
• ae13fe9 Release 1.5.1 (#3613)
• 3dcc4c2 Fix type of flags parameter to GDALOpenEx (#3509)
• 38eb7e5 Trade dealloc for del in DatasetBase (#3612)
• 770b6e2 Fixes for 2 bugs around application of transforms (#3609)
• d9b96d2 Fix the size check in sieve() (#3606)
• db89b60 Pin sphinx to v8.2.3 (#3608)
• aa40966 CI/DEPS: Update build-wheels and libs in maint-1.5 July 2026 (#3605)
• f05c527 Skip a subdataset test for newest GDAL versions (#3604)
• d4b9b22 Expose tolerance argument in reproject (#3586)
• Additional commits viewable in compare view

Sourced from sentry-sdk's releases.

2.68.0

Important

• We're making enable_logs and enable_metrics no-op with this release (#7177), and they'll be dropped in the next major.

  Previously, enable_logs also controlled automatic logs collection from the logging and Loguru integrations. These integrations now get an integration-level capture_sentry_logs boolean option to allow for more control over the auto-collection. These options are False by default, i.e., nothing is auto-collected without your explicit opt-in.

  Action Needed

  If you had enable_logs set to True:

  • If you were using the sentry_sdk.logger.X API, no action necessary, the API will just work.
  • If you were auto-collecting logs from either LoggingIntegration or LoguruIntegration, the auto-collection will be turned off in this release. You can switch auto-collection on explicitly with:

  import sentry_sdk
  from sentry_sdk.integrations.logging import LoggingIntegration
  from sentry_sdk.integrations.loguru import LoguruIntegration
  sentry_sdk.init(
  integrations=[
  LoggingIntegration(capture_sentry_logs=True),
  LoguruIntegration(capture_sentry_logs=True),
  ],
  )

  If you had enable_logs set to False:

  • If you were using it to gate usages of the sentry_sdk.logger.X API, you'll need to remove the calls entirely or define a before_send_log callback to filter out unwanted logs.

  If you has enable_metrics set to False:

  • Any metrics emitted using the metrics API will be emitted. You'll need to drop them in a before_send_metric or remove the calls to the A...

    Description has been truncated